json patch output in tests still string#1630
Open
suarezrominajulieta wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In base to Andrea's comment:
"fine for now. not in this PR, but make new branch PR in which you create the following E2E for an API that:
has a POST to create a resource
has a PATCH to manipulate such created resource (404 if no resource)
and then make sure using DTO (there is a EMConfig for it), so that, in same generates test, we have a DTO used for POST following a call on PATCH without DTO (ie Patch must use a string representation, at least for now). any case, test should not fail to compile"
i created this pr with a test that proves that. this is one of the success test generated: